Fix makeInstance DI for BackendConfigurationManager #80
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
weakbit
approved these changes
Feb 3, 2026
smirgol
force-pushed
the
fix-backend-configuration-manager-di
branch
from
5470b47 to
5dbf71d
Compare
Author
|
still not a nice solution, but gets the job done |
weakbit
approved these changes
Feb 5, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
ConfigurationUtilityis callingmakeInstanceonBackendConfigurationManager, but that service is defined aspublic: false.Since it requires constructor args for instantiating,
makeInstancethrows an exception.This patch works around the issue and works for typo3 v12 and v13. Had to use reflection though, as the parameter count differs between v12 and v13.